Comms Process Flow: Gather Details
When an entry is created in the CommsRequestHeader table, the Comms Monitor Job is triggered to process the comms request and gather and record comms request details. This job:
- Works out the appropriate delivery method. The Delivery Method chosen depends on:
- The delivery methods that are associated with the comms. So if only one delivery method is configured then that is the chosen delivery method.
- Whether the customer
In the context of the Cloud Monetisation Platform, an individual or organisation who has signed an agreement to take goods and services from a service provider. A customer receives a bill associated with one or more subscriptions, and can be a single end user or a large company with many subscriptions assigned to one agreement. has opted in to receive comms. - The communications preference selected by the customer. This is relevant if there are multiple delivery methods associated with a communication. For example, if SMS
Short Message Service.
A text messaging service component of most mobile telephone systems. SMS uses standardized communication protocols to enable mobile phone devices to exchange short text messages. and Email are configured as delivery methods, and the customer preference is SMS, then they will receive an SMS.
-
Determines the target, for example a mobile number, email address etc.
- Derives the values of the default fields that are associated with the communication.
- Once the details are determined, creates an entry in the CommsRequestTargetDistribution table with the status A (Awaiting Merge).
- In the case of push notifications, online notifications and SMS delivery methods, the job also merges the data of the derived fields with the message template to produce the actual message. For letters and email, this merging is carried out by separate jobs.
The sections that follow describe these steps in more detail.
The Comms Request job gathers details such as the delivery method, targets and default field values.